Skip to content

docs: synchronize R1/R2/R3 delivery plan (#66) - #70

Merged
jjangg96 merged 7 commits into
mainfrom
orca/release-reframe
Sep 9, 2026
Merged

docs: synchronize R1/R2/R3 delivery plan (#66)#70
jjangg96 merged 7 commits into
mainfrom
orca/release-reframe

Conversation

@jjangg96

@jjangg96 jjangg96 commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

Change

Synchronize repository planning docs with the maintainer-accepted three-release sequencing in #66. Release classification is now the user-visible sequence; historical M0–M5 Stage/milestones, original Goal text, Agent history and native parent/blockedBy edges are retained.

This is documentation only. It does not implement the daemon/CLI, authorize live App/Keychain/launchd/runner/Docker/Lima operations, or mark G01 complete.

Fixes #66

Delivery map

Release Operator-visible exit Full-original issues R1 vertical children
R1 Internal MVP this Mac, one org, one private repo, existing Linux-container backend, capacity 1, manual App, foreground command, plus full G01 ACK/acquisition/JIT recovery #1 #3 #30 #44 #46 #47 #50 #52 #54 #60 #61 #64 #66 #67 (of #2), #68 (of #13), #69 (of #16)
R2 Everyday operations install/start/stop/status, restart recovery, bounded scaling #4 #5 #6 #7 #9 #10 #12 #13 #14 #15 #20 #40 #68 is a subset of #13/#4#15, not completion
R3 General distribution multi-org, additional native backend, automated onboarding, distribution #2 #8 #11 #16 #17 #18 #19 #67 subset of #2; #69 subset of #16
Future optional VM/multi-host research #21 none

#1 exact Goal is unchanged and remains In progress. #2 remains In progress on R3. #68 stays Blocked by #60/#66/#67 until the minimal foreground contract is reviewed; daemon/install are not implemented. Relabeling does not bypass native dependencies (including G20 still blocked by #17/#18).

Main author Grok 4.6 xhigh; independent review Luna max. Historical Astra/Luna records and live #1/#2/#60 Agent values are unchanged.

Native relations audit (no further edge edits)

Verified live Project #2 = 36 items.

Issue Parent blockedBy Blocks
#67 #2 none #68
#68 #13 #60, #66, #67 #69
#69 #16 #1, #68 none
#66 none none #68
#60 none #54 #68

Original G04 blockers (#1/#2/#3) and G13 blockers (#6/#9/#10/#11/#12) are unchanged. Ask before adding more children or changing #60's missing native parent.

Validation

Prose-only change; no synthetic application tests.

  • jq empty docs/backlog.json
  • git diff --check
  • relative markdown link check
  • live 36-issue map matches Project item-list + GraphQL parent/blockedBy
  • diff limited to AGENTS.md, README.md, docs/{PLAN,BACKLOG,EXECUTION,HANDOFF,ISSUES,backlog.json}

Gaps

  • Independent Luna max review of this PR is still required (not dispatched here; no subagents).
  • Exact-head Codex review and hosted CI must complete before merge.
  • [R1] Deliver one foreground command for a bounded single-worker lifecycle #68 remains Blocked; this PR is not implementation permission.
  • No live authorization.
  • Project Agent field still has no Grok 4.6 xhigh option; override lives in issue bodies.

Rollback

Revert this PR / delete branch orca/release-reframe. Do not remove the already-applied Release field, release:* labels, or #67/#68/#69 native relations unless the maintainer explicitly reverses that mapping. Original issue bodies, statuses and historical edges remain in GitHub.

Review / merge

Do not merge until independent Luna max review is recorded and the exact current head has a clean Codex verdict plus required CI. After merge, #68 is still blocked by #60 and #67.

Map the maintainer-accepted three-release sequencing onto the existing
issue inventory without changing G01's recovery Goal, native parent
edges, or historical M0-M5/Agent records.
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 8, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-09T01:31:21.003110Z bec9c0a Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@jjangg96

jjangg96 commented Sep 8, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b76e54c1f1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/PLAN.md Outdated
Comment thread docs/backlog.json Outdated
Comment thread docs/HANDOFF.md Outdated
Comment thread docs/PLAN.md Outdated
Skip Project Agent writes for issue-body-only Grok overrides, keep #68
contract-first without new native edges, and add a keyed G01g backlog
record so #68 dependencies resolve.
@jjangg96

jjangg96 commented Sep 8, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ee4d47b68e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/HANDOFF.md
Distinguish implementer selection from reviewer selection in the
handoff prompt, dispatch text and verification checklist.
@jjangg96

jjangg96 commented Sep 8, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dbd20b1c2c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/backlog.json Outdated
Keep #60's native blockedBy #54 resolvable in backlog.json without
copying runtime evidence.
@jjangg96

jjangg96 commented Sep 8, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 29f54e9c67

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/PLAN.md Outdated
Restrict #68 to reviewed contract and offline evidence until full #1
and #2 pass. Native blockedBy stays #60/#66/#67.
@jjangg96

jjangg96 commented Sep 9, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9df9eaad00

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/PLAN.md
Comment thread docs/EXECUTION.md Outdated
State that R1 is not independently deliverable until R3-placed full
G02 passes, and that JSON status/agent are historical snapshots.
@jjangg96

jjangg96 commented Sep 9, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b16f52bc65

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/HANDOFF.md Outdated
Replace the #66-#69 skip list with operator-inspected IMPLEMENTER_OVERRIDE
and live Project field-list exact match.
@jjangg96

jjangg96 commented Sep 9, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 🚀

Reviewed commit: bec9c0ae07

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@jjangg96

jjangg96 commented Sep 9, 2026

Copy link
Copy Markdown
Contributor Author

PR #70 final historical-finding and acceptance audit

Date: 2026-09-09 KST
Audit reviewer: Luna max (independent)
Repository: 1XP-AI/gh-runnerd
Issue: #66 — Reframe delivery into MVP, operations and distribution releases
PR: #70
Reviewed head: bec9c0ae074d5ad70a9a45e613137f8bbd86446c
Base: 31ae8102f6f20f8e79258eb824af1400eba21954

Verdict

PASS for the exact-head historical-finding resolution and issue #66 acceptance
evidence audit.
All ten historical inline findings are resolved by the current
source and focused evidence; no resolution relies on an old anchor being stale.
The exact-head Codex review completed cleanly at bec9c0a and the exact-head
public CI check is successful, as coordinator-verified and recorded below.

This is a read-only audit. It does not merge PR #70, close issue #66, update the
Project, resolve review threads, change a goal, or authorize live operations.
Issue/PR close-out remains a coordinator action after the repository's normal
merge decision. R1 remains explicitly not independently deliverable until
the full G02/#2 gate passes; that gate remains placed in R3 and is disclosed as
a cross-release prerequisite, not solved, waived, or moved to R1.

Audit basis and safety boundary

  • Read AGENTS.md, docs/HANDOFF.md, docs/EXECUTION.md, docs/PLAN.md,
    docs/BACKLOG.md, docs/ISSUES.md, docs/backlog.json, README.md, the
    current issue [Plan] Reframe delivery into MVP, operations and distribution releases #66 body/comments, and the exact current source at the reviewed
    SHA.
  • Used the cached REST inline inventory (ten findings) and issue-comment
    inventory, plus the independent Luna max review/routing reports supplied for
    this audit. No broad review or runtime rerun was performed.
  • Focused checks: clean worktree at the reviewed SHA; git diff --check against
    the PR base; valid docs/backlog.json; all machine dependency keys resolve;
    current routing stub cases; 36-row live map, 22-record historical backlog
    preservation, and native relation checks. The latter map/preservation/native
    checks are the latest independent routing-review evidence and were not
    duplicated here.
  • No repository source, runtime, CI, issue, Project, goal, runner, Docker,
    Keychain, launchd, credential, or live GitHub state was changed.

Historical finding resolution

The table uses current-head source and focused reproduction/evidence. Finding
age, anchor movement, stale flags, or an untimestamped reaction is not used as
proof of resolution.

# / severity Historical finding URL and concern Current-head source resolution Focused test / evidence
1 / P1 r3958947063 — R2's complete original acceptance was presented as an independently sequenced exit despite R3 blockers on #4, #13 and #20. PLAN.md states that the R2 set is not independently shippable before its native R3-placed blockers and preserves #20's #17/#18 edge; ISSUES.md records the live rows and blockers. Source cross-check of the R2 exit, all 36 mapped rows, and native edges passed in the independent review. No dependency was weakened or reclassified as Done.
2 / P2 r3958947071 — machine-readable #68 dependency used raw #60 instead of a resolvable key. backlog.json adds keyed G01f/G01g records; G13-R1 depends on keyed G01g, P66, and G02-R1. Focused jq validation: every dependencies value resolves to a record key; no machine dependency value starts with #. Result: pass.
3 / P1 r3958947075 — an issue-body-only Grok override could be replaced by Luna in the Project Agent field. HANDOFF.md derives the intended implementer from the inspected override, exact live option match, and Ready/conflict guards; an unsupported explicit override skips the edit and preserves the field. The independent routing review passed the stub-GitHub cases for default Luna, unsupported Grok, supported override, changed former child override, conflict, non-Ready, and unset override. No live item-edit was issued.
4 / P1 r3958947083#68 could enter production implementation after #60/#66/#67 while full G01/G02 remained open. PLAN.md, BACKLOG.md, and EXECUTION.md limit #68 to reviewed contract/offline evidence until full #1/#2 pass; production starts only after both gates. Current-source contradiction check passed: no checked-in #68 path authorizes production before full G01/G02. Native blockers remain #60/#66/#67.
5 / P1 r3959069034 — override issues could select Grok as the independent reviewer. EXECUTION.md and HANDOFF.md separate implementer override from the required independent Luna max review, including the reusable dispatch prompt. Independent-review policy cross-check passed: current #66/#67/#68/#69 override is Grok implementer, Luna remains reviewer; current source contains no reviewer substitution.
6 / P2 r3959187193 — keyed G01g record omitted its native G01f/#54 blocker. backlog.json records G01f for #54 and G01g's dependency as G01f; ISSUES.md retains #60 blockedBy #54 and #60#68. Focused key-resolution and native-edge checks passed; the independent review confirms the 22 original records and native relations were preserved.
7 / P1 r3959289007 — repeated #68 production-gate finding after fresh evidence. Same direct resolution as finding 4: PLAN.md and backlog.json explicitly restrict #68 to contract/offline evidence before full G01/G02 and preserve the native blockedBy set. Independent Luna source audit reproduced the gate wording at the exact head; no stale-anchor argument was used.
8 / P1 r3963629069 — full G02 is R3-placed, yet it gates the R1 executable path. PLAN.md, README.md, and HANDOFF.md disclose that full #2 remains R3, is a mandatory pre-release gate for #68 production, and means R1 is not independently deliverable. Acceptance/source audit confirms the prerequisite is disclosed as a cross-release gate, not solved, waived, or moved to R1. This is an intentional remaining release limitation, not an unresolved documentation contradiction.
9 / P2 r3963629073backlog.json statuses appeared to contradict the live Project map. backlog.json declares status and agent as the initial historical planning snapshot, names Project #2/current issue bodies as live dispatch authority, and forbids redispatch from the snapshot; EXECUTION.md repeats that contract. 22 original records remain preserved; the 36-row live map and status distinction were independently checked. No historical status was silently rewritten.
10 / P2 r3963725078 — hard-coded issue-number routing could mishandle future or changed model overrides. HANDOFF.md requires inspected IMPLEMENTER_OVERRIDE, exact live Agent-option matching, preserves the field for unsupported explicit overrides, and states the script does not branch on issue numbers. The independent routing review passed all stub-GitHub cases and checked the absence of the old issue-number branch. No Project mutation was performed.

Issue #66 acceptance audit

The current issue body is the authority for the five acceptance items. The
maintainer's issue comments confirm that the release field, 36-item map and
R1 child/native relations were additive and that original planning records and
gates remain in force: release reorganization
and R1 relations.

Issue #66 acceptance Verdict at exact head Current source Test / evidence
Three release stages and concrete user-visible exit criteria documented. PASS PLAN.md defines R1 operator exit, R2 operations target, R3 distribution target and Future research; README.md mirrors the user-visible split. Source audit found concrete scope and limits without claiming implementation or live evidence.
All current issues mapped, native dependency updates only where justified, and no false Done states. PASS ISSUES.md contains the 36-row live release map and verified native relations; BACKLOG.md preserves the original full-scope backlog; backlog.json contains only additive keyed child/planning records. Independent review passed map36rows, old22records, and nativeedges checks; machine dependency key resolution and JSON validation pass. No native edge was added or changed by this audit.
Minimum executable MVP critical path identified, with unimplemented CLI/daemon/install work explicit. PASS (planning evidence) PLAN.md identifies the one-host/one-org/one-private-repo/one-worker path and explicitly excludes daemon, install, launchd, native jobs, second backend and general scheduling; README.md says the commands are intended interfaces and there is no runnable product. Documentation-only diff; no runtime implementation or live operation is claimed.
Existing G01 full objective preserved; no live evidence represented as complete. PASS PLAN.md retains the evidence gates and G01 row; BACKLOG.md keeps G01 full and #68/#69 gated. Current map records #1 as In progress and explicitly says child slices/happy-path work do not complete G01. No live App, runner, Docker, Keychain or launchd operation occurred.
Focused independently reviewed PR, exact-head clean Codex verdict and CI before merge. PASS (pre-merge gate evidence; close-out pending) AGENTS.md and EXECUTION.md require independent review, exact-head Codex and CI. Exact-head Codex completion: review comment, reviewed bec9c0ae07; summary, completed at 2026-09-09 01:31:21Z for bec9c0a; exact-head Go checks completed successfully. This audit does not merge or close the issue.

Remaining gaps and explicit non-claims

  1. Close-out is pending. PR docs: synchronize R1/R2/R3 delivery plan (#66) #70 remains unmerged and issue [Plan] Reframe delivery into MVP, operations and distribution releases #66 remains open;
    this audit intentionally performed no merge, Project, issue, comment, goal or
    review-thread mutation.
  2. R1 is gated, not independently shippable. Full G02/[G02] Prove local App enrollment and launchd credential access #2 remains a
    mandatory R1 pre-release gate while retaining its R3 full-scope placement.
    This is explicitly disclosed in current PLAN/BACKLOG/HANDOFF/README source;
    it is not treated as solved or waived.
  3. Full G01/G02 evidence remains open. [R1] Deliver one foreground command for a bounded single-worker lifecycle #68 production implementation is
    unauthorized until both full gates pass; only reviewed contract/offline
    evidence is allowed before then. [R1] Qualify the internal MVP with an authorized real job and recovery evidence #69 remains blocked by full [G01] Prove Scale Set delivery, acquisition and drain contracts #1 and [R1] Deliver one foreground command for a bounded single-worker lifecycle #68.
  4. Historical CI failure is not attributed to this docs change. The prior
    exact-head 9df9eaad... run's paired-terminal deadline failure remains a
    historical runtime result. PR docs: synchronize R1/R2/R3 delivery plan (#66) #70 changed planning/documentation only; it
    neither root-caused nor claimed to fix that runtime failure. The current
    bec9c0a CI result above is the applicable docs-head check.
  5. No live evidence is implied. Existing manual runners, Docker/Lima,
    Keychain, launchd, GitHub App credentials, workflows and runner groups remain
    outside this read-only audit.

@jjangg96
jjangg96 merged commit 959b71f into main Sep 9, 2026
1 check passed
@jjangg96
jjangg96 deleted the orca/release-reframe branch September 9, 2026 02:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Plan] Reframe delivery into MVP, operations and distribution releases

1 participant